Skip to content

ci(release): attach each release's tarball and provenance - #38

Merged
qddegtya merged 1 commit into
developfrom
feature/signed-release-assets
Nov 2, 2026
Merged

qddegtya merged 1 commit into
developfrom
feature/signed-release-assets

Conversation

@qddegtya

@qddegtya qddegtya commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

OpenSSF Scorecard reports Signed-Releases: no releases found. We have 36 GitHub Releases, but Scorecard only counts releases that carry files, and ours had none.

scripts/release/attach-assets.mjs attaches three files to every @hlang-org/* release:

  • <pkg>-<ver>.tgz: the registry tarball, verified against dist.integrity (SHA-512).
  • <pkg>-<ver>.sigstore.json: the Sigstore bundle of the SLSA v1 provenance that npm recorded through trusted publishing.
  • <pkg>-<ver>.intoto.jsonl: the DSSE in-toto envelope from that bundle.

Nothing is signed by us; every file comes from the registry. The script runs as its own release.yml step on every push to main and is idempotent, so it also backfills past releases. Versions published before trusted publishing have no provenance; they are reported and left untouched (15 of 36).

Verification

  • --dry-run against the live registry: 21 releases verified (integrity matches), 15 skipped.
  • For editor-ui 0.6.0, the in-toto statement's subject SHA-512 equals the tarball's, and its builder is hlang-tech/hlang/.github/workflows/release.yml@refs/heads/main.
  • npm audit signatures verifies the installed packages.
  • lint:docs reports 0 issues.

Docs

  • SECURITY.md gains a "Verifying a release" section, and its supported-versions table is corrected (runtime and interpreter are 2.x).
  • CONTRIBUTING mentions the assets.

🤖 Generated with Claude Code

Every @hlang-org GitHub Release now carries the tarball it released
(checked against the registry's integrity hash), the Sigstore bundle of
the SLSA provenance npm recorded at publish time, and the in-toto
attestation inside it. Nothing is signed by the script; every file comes
from the registry. The step runs on every push to main and is idempotent,
so it also completes past releases; versions published before trusted
publishing have no provenance and are left as they are.

SECURITY.md explains how to verify a release, and its supported-versions
table now says runtime 2.x and interpreter 2.x.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
hlang Ready Ready Preview Nov 2, 2026 2:37am UTC

Request Review

@qddegtya
qddegtya merged commit 1c9df8c into develop Nov 2, 2026
6 checks passed
@qddegtya
qddegtya deleted the feature/signed-release-assets branch November 2, 2026 02:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant